Hi All,   I would like to import qtree and user quota rules and policies from an existing FAS cluster to volumes moved using SnapMirror to a different cluster. The current quota database number is 487. Is there a command or ONTAP Toolkit that can help me with this?   Thanks in advance   Zoltan  ... View more

I followed the .\backupSharesAcls.ps and .\restoreSharesAcls.ps1 script to backup the share and ACL permissions from source volume and restore it on destination volume. Does the restore snapmirror destination should also have same SVM name as in production ? I created same volume name and namespace in destination but SVM name is different . Getting error record doesnt match. .\restoreSharesAcls.ps1 -server <clus_mgmt> -user <uname> -password <> -vserver <destination-vname> -shareFile C:\share.xml -aclFile C:\acl.xml -spit less   Please advise on this. @scottharney    ... View more

Hello all,   Long story short.   The issue is that Logstash is duplicating logs after application restarts due to PVCs being mounted with different minor device versions, causing Logstash to mistakenly treat the same log files as different. Having said that, I’d like to know if it's normal for the 'minor device number' of an NFS 4.0 volume to change when it’s mounted multiple times.   This appears to be a known issue when working with Network File Systems, as outlined in the Elastic documentation I found online, this happens because NFS can present different minor device versions, which Logstash interprets as different file systems, leading to log duplication: https://www.elastic.co/docs/reference/logstash/plugins/plugins-inputs-file#_reading_from_remote_network_volumes   If any of you folks have a second opinion on this, I'd love to hear it.   Thank you very much,   Joel. ... View more

I have a query regarding the compatibility between nfsd and glibc. In our system, we've upgraded glibc to version 2.40 and are using NFS version 2.1.1 with NFSv3. Previously, with glibc 2.23, everything was working fine, and we weren’t using libtirpc. However, after the glibc upgrade, libtirpc was included and enabled in NFS as well. Now, none of the NFS-related services (nfsd, rpc.statd, rpc.mountd, portmap) are running. When attempting to start nfsd, the following errors occur: "unable to set any sockets for nfsd" "writing fd to kernel failed: errno 89 (Destination address required)" or "errno 111 (Connection refused)" Console logs show: "svc: failed to register nfsdv3 RPC service (errno 111)." After upgrading glibc, the --enable-obsolete-rpc option has been removed from glibc. Can anyone provide guidance on how to debug or resolve this issue? ... View more